Added variable vic_vm_alert_service_name for vmalert service name #67
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes it needs to start more than one vmalert process with different configs. E.g. running a vmalert for datasource victoriametrics and the other one for datasource loki.
Variable
vic_vm_alert_service_name
give you an opportunity to configure and run several vmalert services.Example playbook:
Also this PR fixing the dry-run mode error, when service is not exists in systemd (first dry-run on fresh server).